This forum is closed to new posts and
responses. The content has been migrated to the Digital Solutions Community. Please join us there for new content as well as this content. For customer support, please visit the official HCL customer support channels below:
In the vault limitations, we can read that Smartcard-enabled IDs cannot be stored in a vault. A new user ID, which has not been smartcard-enabled yet, is loaded into the vault. If the user ID is smartcard-enabled after the initial vault upload, what happens if a rename, recertification or key rollover is done? Do we need to disable the smartcard protection and enable it after the action?
Feedback response number TKLR8UCGTZ created by ~Ben Nonkioden on 05/16/2012